Birmingham City Council
Tree preservation zone
There is a problem
- 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset
THE BIRMINGHAM (152 - 160 HAGLEY ROAD, EDGBASTON) (No. 2) TPO 1994
- reference
- 658
- name
- THE BIRMINGHAM (152 - 160 HAGLEY ROAD, EDGBASTON) (No. 2) TPO 1994
- tree-preservation-order
- TPO 658
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.938283 52.470843,-1.937052 52.470926,-1.937004 52.471128,-1.937013 52.471559,-1.937025 52.471560,-1.937036 52.471796,-1.937022 52.471932,-1.937904 52.471903,-1.937895 52.471311,-1.938308 52.471284,-1.938273 52.471227,-1.938186 52.471179,-1.938142 52.471109,-1.938147 52.471086,-1.938215 52.471017,-1.938257 52.470950,-1.938283 52.470843)))
- point
- POINT (-1.937546 52.471361)
- notes
- The shaded area represents those properties which fall within the outline of a Tree Preservation Order. To precisely identify trees protected by the Order, you can request a copy of the tree preservation order at the following link.
- organisation
- entry-date
- 2025-11-30
- start-date
- end-date
How to fix this issue
Your dataset is missing the tree-preservation-order column.
The Tree preservation zone guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that covers this zone.
How to improve Birmingham City Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL